A: Under software Release 2 the operators in PostScript that modified files were deliberately disabled. These operators are
\b file
\b0 ,
\b deletefile
\b0 , and
\b renamefile
\b0 . These operators are disabled in the appkit when creating new PostScript contexts. Whenever a new PostScript context is created, it is created in a "secure" manner. A secure context is one that cannot modify files on the UNIX file system. All new PostScript contexts are secure by default.\
\
There's a way to circumvent this if you absolutely must write files from the Window Server. You can use an appkit function to create non-secure PostScript contexts within your application.\
\b0 . This routine creates a new PostScript context which allows you to modify files on the file system.\
\
Developers should understand the security implications of creating these contexts: PostScript code executed in a non-secure context can write into a user's files. Again, writing files from the Window Server is not a preferred way for application writers to communicate information back from the Window Server to their application.\
This functionality is provided primarily for those developers who have code that already relies on these PostScript operators.\
\fc0 \
A new version of the
\b pft
\b0 program is available from NeXT Developer Support. The new
\b pft
\b0 allows PostScript programs and programmers to use file operators. It is not intended as a workaround for applications or application users. Application writers should use
\b _DPSCreateContext()
\b0 . Application users need to get a new copy of the application which uses